2016-06-14 - 27465 - Break Fix - EDI110 bug fix #CrystalReportsSupport

BREAK FIX

27465 - EDI110 bug fix

Problem Summary


Need to fix EDI110 report display Non-EDI orders in BI Production.

Admin Info


Purpose
Need to fix EDI110 report display Non-EDI orders in BI Production.
Requested by
Ashley Melcher
Issue Date
06-14-2016
Resolved by
Dhananjay G
Resolved Date
06-24-2016
Document Status
Complete

Detailed Problem Description


IM from Saravanan on 06/14/2016:

EDI110 - this report seems to show some non EDI accounts as well and also check is there any logic to include ZS and ZD. It should not show non EDI orders.
For Ex: SO 3155768 this order should not show up on EDI110 report.

Solution Analysis and Recommendations


1. Need to check any logic is added in the report for displaying non EDI accounts.
2. Need to analyze the non EDI accounts identification key figure at ECC tables level.
3. Need to add days prompt in the report.
4. Need to modify the logic in the report for restricting Non EDI accounts also.
5. Need to validate the report with ECC tables.

Test Plan
Test ID
Test Scenario
Expected Results
1
Report Format.
Should be as per NEC crystal standard checklist.
2
Execute Crystal Report in Crystal Designer tool after changes.
Report should execute successfully in Crystal Designer tool.
3
Schedule the Report in NEC BI Launch Pad.
Report should execute successfully in NEC BI Launch Pad.

Resolution

1. Checked any logic is added in the report for displaying non EDI accounts.
2. Analyzed the non EDI accounts identification key figure at ECC tables level.
3. Added 'Days' prompt in the report.
4. Modified the logic in the report for restricting Non EDI accounts:
if {VBAK.LIFSK} in ["ZD", "ZS"] then
(
((not({VBAP.WERKS} = "9010" and {VBAP.ABGRU} = " ")) or ({VBAP.ABGRU} in ["ZD", "ZS"])) and
(if {VBAK.VGBEL} in '0040000000' to '0049999999' Then
{VBAK.ERDAT} >= currentdate - {?Days} else
{VBAK.AUDAT} >= currentdate - {?Days}) and
{TVKOT.SPRAS} = "E" and {TVGRT.SPRAS} = "E"
)
5. Validated the report with ECC tables successfully.
6. Placed the report in BI development and promoted it to BI Production after successful validation.

Release Information


2016-06-24 - 27465 - Rel Notes - EDI110 bug fix